Skip to content

fix(deps): bump dd-trace to 6.24.0 and 5.135.0 for CVE-2026-116693 - #860

Open
pablomartinezbernardo wants to merge 1 commit into
mainfrom
pmartinez/dd-trace-6.24.0-5.135.0
Open

pablomartinezbernardo wants to merge 1 commit into
mainfrom
pmartinez/dd-trace-6.24.0-5.135.0

Conversation

@pablomartinezbernardo

Copy link
Copy Markdown
Contributor

What does this PR do?

Updates the bundled dd-trace versions to 6.24.0 for Node 22+ and 5.135.0 for Node 18/20, and aligns the optional npm peer ranges. Regenerates yarn.lock and refreshes the local integration snapshots for the newer tracers.

Removes the import-in-the-middle 3.4.0 resolution so both tracer lines use their declared 3.5.3 loader.

Motivation

Includes the bundled-tracer security updates proposed in #859 for CVE-2026-116693. Customers using the Lambda layers cannot replace the tracer bundled inside them.

Testing Guidelines

The final Git tree is identical to #859 at ad7621791ee1b1c3316e54d49b3304832969b189, where all five GitHub Actions workflows passed:

Local Docker validation also passed: Node 22 had 54 suites / 732 tests passing; Node 20 had 53 suites / 730 tests passing, with two runtime-specific tests skipped. Formatting, lint, the dependency-installer check, freshness, and packed npm-package checks passed.

CI will run again on this new commit. Real AWS end-to-end tests and GitLab publishing jobs have not been validated by these results.

Additional Notes

Recreates #859 on an upstream branch with one signed commit. Credits @dirkluijk for the original dependency update, loader fix, and snapshot changes.

Types of Changes

  • Bug fix
  • New feature
  • Breaking change
  • Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

  • This PR's description is comprehensive
  • This PR contains breaking changes that are documented in the description
  • This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
  • This PR impacts documentation, and it has been updated (or a ticket has been logged)
  • This PR's changes are covered by the automated tests
  • This PR collects user input/sensitive content into Datadog
  • This PR passes the integration tests (ask a Datadog member to run the tests)

Update both tracer lines bundled by the Lambda layers and keep the npm
peer ranges aligned with the Node 18/20 and Node 22+ runtime split.

Refresh the local integration snapshots and remove the import-in-the-middle
override so each tracer uses the loader version it declares.

Co-authored-by: dirkluijk <mail@dirkluijk.nl>

@datadog-datadog-prod-us1-2 datadog-datadog-prod-us1-2 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

The upgraded tracer pins, peer ranges, and lockfile remain consistent with the Node 18/20 versus Node 22+ layer selection. Runtime compatibility was assessed statically; full runtime suites were not rerun.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 74edf1f

@rithikanarayan rithikanarayan left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Pipelines

❌ Errors

Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 1 Pipeline job failed

DataDog/datadog-lambda-js | e2e-test-status

View more details · View in GitLab

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 74edf1f | Docs | View more details | Give us feedback!

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants